Skip to content

ci(release): fix duplicate tag error in multi-crate workspace#74

Merged
subotic merged 1 commit into
mainfrom
feat/batch-cli-improvements
Mar 20, 2026
Merged

ci(release): fix duplicate tag error in multi-crate workspace#74
subotic merged 1 commit into
mainfrom
feat/batch-cli-improvements

Conversation

@subotic

@subotic subotic commented Mar 20, 2026

Copy link
Copy Markdown
Owner

Closes #74

Motivation

The v0.2.0 release failed because release-plz tried to create the v0.2.0 tag twice — once for loom-core and once for loom-cli. The second attempt got "Reference already exists". This also caused loom-cli to not be published to crates.io.

Summary

  • Disable git_tag_enable at workspace level
  • Enable it only on loom-cli (the primary package that owns the tag)
  • loom-core inherits the disabled default — no tag created for it

References

Test Plan

  • Config matches the documented single-tag pattern
  • Next release creates only one tag and publishes both crates

release-plz was creating the same v{{ version }} tag for both loom-cli
and loom-core, causing "Reference already exists" on the second crate.

Fix: disable git_tag_enable at workspace level, enable it only on
loom-cli (the primary package). loom-core inherits the disabled default.

See: https://release-plz.ieni.dev/docs/extra/single-tag
See: release-plz/release-plz#2292

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@subotic subotic merged commit 2123bd7 into main Mar 20, 2026
6 checks passed
@subotic subotic deleted the feat/batch-cli-improvements branch March 20, 2026 23:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant